New Relic

New Relic helped us identify RDS lock wait timeouts for a clients high load e-commerce store. With the help of New Relic Application Performance Monitoring we were able to pin point the root cause and made changes to the table configurations of DB which helped us solve the degraded site performance.

After GA4 retired the page speed reports, we installed New Relic on our site to make sure we didn't lose visibility into page load times. We quickly realized that it has a lot more capabilities than we were using or would ever use. It's a very powerful tool, but more for technical users.

We use New Relic for monitoring back-end / front-end performance and synthetic monitoring. It gives us insight using custom dashboards, connections to other services and gives teams opportunity to focus on their part as well as giving them insight on the whole. Also it gives us the alerting to pro-actively act on possible issues before they become problematic.

NR is used as a monitoring and optimisation tool at our organisation. It integrates with several of our key other services such as AWS and helps development and support teams keep on top of their applications through the monitoring options and alerting / notification features. Lots of great visualisation options and customisation abilities to make it fit exactly what you do at your company. It helps us reduce MTTR and often catch issues before they become incidents which is very valuable for a company like ours when any amount of downtime can have a big knock on effect to our customers.

We use New Relic across the whole organization to gather data from our hosts: - Alert in case of performance degradation - Understand the call stack and find where performance issues come from - Link services between them

we are using many new relic sub products for our many use cases we are using it as APM tools, infrastructure monitoring tool in order to monitor our large number of server fleet, Database monitoring, Kubernetes Cluster monitoring, track bugs and issues in application code, alerts and warnings for uptime of our application or to get the overall idea on how our product is performing under certain circumstances and for better scaling and resources optimisations.

We use New Relic to get stats on page hits and performance metrics of our website, hosted on Acquia. We use it to monitor slow SQL queries and also page load times and get statistics on browser types as well as what device is accessing our site's pages. It is also the default performance monitoring tool for Acquia sites.

We have used a couple of different tiers of New Relic. Our Dev Ops manager first used it to track all bugs, issues, and uptime, giving us alerts and warnings to help us proactively manage our applications. Now we use it more as a traffic monitoring tool, helping us know how our server is performing against traffic and demand.

Our solution hosts thousands of PHP applications in AWS cloud across multiple regions. We installed the PHP NewRelic agent and we set up each application to use a different newrelic_set_appname among with several newrelic_add_custom_parameter, like the database identifier where the site is in, the Autoscaling group where the site is running on, etc., that way we could identify which clients had the most traffic in a specific database server or Autoscaling group. To do that, we used Dashboards with queries to retrieve that data. NewRelic APM helped us a lot to identify why a site was slow when loading in the browser or when processing a specific php script. With Transactions and Databases features, we could even identify which specific php function of the code was stuck or which specific database query was taking too long. With External Services, we could detect when there was a delay connecting, for example, to Microsoft auth, Google auth, or even to another AWS service. In general, for us, it was a great tool to troubleshoot application slowness issues.

• Infrastructure Monitoring and Alerting
• Application Performance Monitoring and Alerting
• Tracking business and product related KPI's and metrics.
• Dashboards for NOC and the customer facing teams.

New Relic is the de-facto KPI tracking and dash-boarding tool for us. Apart from the APM - which is the USP of New Relic - even the technical and product KPIs are plotted on New Relic. It is used the tool for handshake and exchange of data between the various groups within the organisation.

New Relic is being used in our Organization for monitoring everything literally. All our devices & instances, whether they are present in AWS, GCP, or On-premises, are being monitored in New relic. New Relic has helped in making sure that all aspects of an instance are being monitored, and whenever something goes wrong, New Relic sends out an alert over email or any chosen platform.

New Relic is used for real-time monitoring + Synthetic Monitoring.

New Relic is primarily used for Application Performance Monitoring (APM) and Synthetic Monitoring. Their APM offering gives key insights into the health and performance of the company's web infrastructure. It is used to identify code bottlenecks, timeouts, and any requests or issues that are placing a heavy burden on the server. Additionally, it can be used to identify endpoints or requests that are causing poor customer experiences due to being slow or erroring. Synthetic Monitoring is used to evaluate whether certain functional features are working.

We use New Relic to set up dashboards to track errors, throughput, and performance. We also set up synthetic monitors and alarms to make sure our site pages are up and running.

New Relic gives us the monitoring and instrumentation capabilities to support a high transaction eCommerce platform and back-office functions. It gives us performance analysis on every new deployment and quickly provides us metrics and diagnostic logs to facilitate our investigation into any issues that arise. Its alerting means we have eyes on the system even out of hours and can help us protect revenues.

We use New Relic to monitor our microservices, within an internal platform to manage them. The business provides financial products like payment, credits, accounts, transfers, etc, a shopping platform to sell products that extends to multiple countries, shipping logistics of those sells with warehouse management, and last-mile control.

New Relic is our platform of choice for the observability of our microservice architecture. Constantly spinning up and down microservices and understanding how they are performing in production is a critical need for our Engineering team. New Relic makes it easy for us to monitor our services and quickly identify any triage issues.

I use New Relic in order to monitor and follow KPI about our application. Particularly, this allows us to detect performance issues.

New Relic is our main monitoring and APM tool, which allows devs and support to monitor the reliability of our systems. Without New Relic, we'd have to resort to setting up the monitoring and alerting ourselves, and I believe New Relic has been a critical piece of infrastructure that allows us to react quickly when an incident is detected.

New Relic is an awesome tool and a must-have for any engineering team who would like to understand what is going on with their software. We use this software [on] a daily basis. Both the DevOps and the Engineering team use this service. The best thing [about] this tool is it lets you analyze traffic rate, server issues, code issues, page load time, and many more in real-time. This is very useful when there is high traffic on the site or if you would like to understand one particular issue. New Relic helps you to dive deep into the code and pinpoint exactly where the error is happening. I can't imagine running our systems without New Relic!

We mainly use Infrastructure Alerts, Synthetic Checks, and Logging in our department for our web services and websites. Other departments may use other tools, it is independent. I[New Relic] is used to catch infrastructure issues and production errors early. Also, [New Relic,] helps us understand how our services are used externally, and how they perform.

The most important use of New Relic for us is API monitoring. With NewRelic we have a real-time update about the APIS health, so we have configured alerts that trigger messages in google chat when some API is not running well. Also, it helps a lot in problems investigations, providing a lot of data to understand what is going on. We have minimal use in frontend applications too, to monitor the performance of our SPA.

New Relic is used across engineering departments to monitor how systems operate in both non-prod and production environments. For the component that I own, I use it to monitor Tomcat health (like the number of thread pools) and monitor the latency/error rate of the requests that my service handles. This helps us to understand how our system behaves, how much our system can handle, and help in capacity planning. I also set up important alert signals based on New Relic data and route the signal to Pager Duty that we have engineers on a routine schedule to pick up those alerts when something unexpected happened in production. This helps to quickly mitigate production issues that can surface to end-users

We are using New Relic ONE throughout our whole organization for monitoring our microservice health and performance. APM is one of the most important features in New Relic we rely on to analyze our application overall quality after every deployment including memory and CPU usage, networking transaction, and error ratio. We create different alerts based on the metrics and query results to notify the team through the paging system, so we can solve issues immediately. The metrics are very accurate in real-time and help us to identify the issues quickly. The configuration to apply New Relic APM and Browser features are somewhat difficult. We have both Java and NodeJS based applications and when applications can not connect to New Relic, the log message doesn't describe where/how it's failing.

New Relic is being used for an added layer of platform health monitoring by my clients. It is used to capture performance metrics and analyze the data to keep an eye on performance trends and action on any negative performance. It gives them a view of the platform and remote services performance that they would otherwise have to use multiple portals to view and gain access to.